Method and system for managing a nand flash memory

ABSTRACT

A method and system to facilitate paging of one or more segments of a logical-to-physical (LTP) address mapping structure to a non-volatile memory. The LTP address mapping structure is part of an indirection system map associated with the non-volatile memory in one embodiment of the invention. By allowing one or more segments of the LTP address mapping structure to be paged to the non-volatile memory, the amount of volatile memory required to store the LTP address mapping structure is reduced while maintaining the benefits of the LTP address mapping structure in one embodiment of the invention.

FIELD OF THE INVENTION

This invention relates to memory management, and more specifically but not exclusively, to improve the management policies of a NAND flash memory.

BACKGROUND DESCRIPTION

The use of non-volatile media such as NAND flash memories in computer platforms has been increasing. A large and flat logical indirection system map such as a logical-to-physical address mapping table can be used for the management of NAND flash memories in solid state drives (SSDs) and caches. The logical-to-physical address mapping table requires a fixed capacity ratio of a volatile memory to a NAND flash memory. For example, in a platform that assigns four kilobytes of the NAND flash memory per page, the volatile memory stores a logical-to-physical address mapping table and a four bytes entry in the table is required for every four kilobytes of NAND flash memory, i.e., approximately one megabyte of volatile memory is required for every one gigabyte of NAND flash memory.

The requirement for the fixed capacity ratio of the volatile memory to the NAND flash memory may be inadequate for platforms bounded by the capacity of the volatile memory, cost of the volatile memory, perception of the need of volatile memory to support management of NAND flash memory, performance and/or product branding constraints.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of embodiments of the invention will become apparent from the following detailed description of the subject matter in which:

FIG. 1 illustrates a system to implement the methods disclosed herein in accordance with one embodiment of the invention;

FIG. 2 illustrates the modules in a system to implement the methods disclosed herein in accordance with one embodiment of the invention;

FIG. 3 illustrates an arrangement of a logical-to-physical address mapping table in accordance with one embodiment of the invention;

FIG. 4 illustrates an arrangement of a lookup table in accordance with one embodiment of the invention;

FIG. 5A illustrates a flowchart of the operations to look up an entry of a logical-to-physical address mapping table in accordance with one embodiment of the invention;

FIG. 5B illustrates a flowchart of the operations to Identify a buffer in a volatile memory to cache a segment of a logical-to-physical address mapping table from a non-volatile memory in accordance with one embodiment of the invention;

FIG. 6 illustrates a pseudo code of the operations to look up an entry of a logical-to-physical address mapping table in accordance with one embodiment of the invention;

FIG. 7 illustrates an optimized lookup table in accordance with one embodiment of the invention;

FIG. 8 illustrates a pseudo code of the operations to look up an entry of a logical-to-physical address mapping table in accordance with one embodiment of the invention; and

FIG. 9 illustrates a flowchart of the operations to recover a logical-to-physical address mapping table in accordance with one embodiment of the invention.

DETAILED DESCRIPTION

Embodiments of the invention described herein are illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals have been repeated among the figures to indicate corresponding or analogous elements. Reference in the specification to “one embodiment” or “an embodiment” of the invention means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. Thus, the appearances of the phrase “in one embodiment” in various places throughout the specification are not necessarily all referring to the same embodiment.

Embodiments of the invention provide a method and system to facilitate paging of one or more segments of a logical-to-physical (LTP) address mapping structure to a non-volatile memory. The LTP address mapping structure is part of an indirection system map associated with the non-volatile memory in one embodiment of the invention. By allowing one or more segments of the LTP address mapping structure to be paged to the non-volatile memory, the amount of volatile memory required to store the LTP address mapping structure is reduced while maintaining the benefits of the LTP address mapping structure in one embodiment of the invention.

In one embodiment of the invention, only some sections or segments of the LTP address mapping structure is located or cached in the volatile memory during the operations of a system. The rest of the segments are stored in the non-volatile memory until the segments are required. In one embodiment of the invention, the LTP address mapping structure includes, but is not limited to, a table, an array, or any other mapping structure to map a logical address to a physical address.

FIG. 1 illustrates a system 100 to implement the methods disclosed herein in accordance with one embodiment of the invention. The system 100 includes, but is not limited to, a desktop computer, a laptop computer, a netbook, a notebook computer, a personal digital assistant (PDA), a server, a workstation, a cellular telephone, a mobile computing device, an Internet appliance or any other type of computing device. In another embodiment, the system 100 used to implement the methods disclosed herein may be a system on a chip (SOC) system.

The processor 110 has a processing core 112 to execute instructions of the system 100. The processing core 112 includes, but is not limited to, pre-fetch logic to fetch instructions, decode logic to decode the instructions, execution logic to execute instructions and the like. The processor 110 has a cache memory 116 to cache instructions and/or data of the system 100. In another embodiment of the invention, the cache memory 116 includes, but is not limited to, level one, level two and level three, cache memory or any other configuration of the cache memory within the processor 110.

The memory control hub (MCH) 114 performs functions that enable the processor 110 to access and communicate with a memory 130 that includes a volatile memory 132 and/or a non-volatile memory 138. The volatile memory 132 includes, but is not limited to, Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM), and/or any other type of random access memory device. The non-volatile memory 138 includes, but is not limited to, NAND flash memory, phase change memory (PCM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), or any other type of non-volatile memory device.

The memory 130 stores information and instructions to be executed by the processor 110. The memory 130 may also stores temporary variables or other intermediate information while the processor 110 is executing instructions. In one embodiment of the invention, the volatile memory 132 has a cached LTP address mapping table 134 and a lookup table 136. In one embodiment of the invention, the entire LTP address mapping table 182 associated with the non-volatile memory 180 is stored in the non-volatile memory 180 and the volatile memory 132 caches one or more segments of the LTP address mapping table 182 in the cached LTP address mapping table 134.

In another embodiment of the invention, the volatile memory 132 caches only some segments of the LTP address mapping table associated with the non-volatile memory 180 in the cached LTP address mapping table 134. The rest of the segments of the LTP address mapping table not cached in the cached LTP address mapping table 134 are stored in the LTP address mapping table 182 in the non-volatile memory 180. In one embodiment of the invention, the lookup table 136 indicates a location of each segment of the LTP address mapping table associated with the non-volatile memory 138.

The chipset 120 connects with the processor 110 via Point-to-Point (PtP) interfaces 117 and 122. The chipset 120 enables the processor 110 to connect to other modules in the system 100. In one embodiment of the invention, the interfaces 117 and 122 operate in accordance with a PtP communication protocol such as the Intel® QuickPath Interconnect (QPI) or the like. The chipset 120 connects to a display device 140 that includes, but is not limited to, liquid crystal display (LCD), cathode ray tube (CRT) display, or any other form of visual display device.

In addition, the chipset 120 connects to one or more buses 150 and 160 that interconnect the various modules 174, 180, 184, 186, and 188. Buses 150 and 160 may be interconnected together via a bus bridge 172 if there is a mismatch in bus speed or communication protocol. The chipset 120 couples with, but is not limited to, a non-volatile memory 180, a mass storage device(s) 184, a keyboard/mouse 186 and a network interface 188. The mass storage device 184 includes, but is not limited to, a solid state drive, a hard disk drive, an universal serial bus flash memory drive, or any other form of computer data storage medium. The network interface 188 is implemented using any type of well known network interface standard including, but not limited to, an Ethernet interface, a universal serial bus (USB) interface, a Peripheral Component Interconnect (PCI) Express interface, a wireless interface and/or any other suitable type of interface. The wireless interface operates in accordance with, but is not limited to, the Institute of Electrical and Electronics Engineers (IEEE) wireless standard family 802.11, Home Plug AV (HPAV), Ultra Wide Band (UWB), Bluetooth, WiMax, or any form of wireless communication protocol.

While the modules shown in FIG. 1 are depicted as separate blocks within the system 100, the functions performed by some of these blocks may be integrated within a single semiconductor circuit or may be implemented using two or more separate integrated circuits. For example, although the cache memory 116 is depicted as a separate block within the processor 110, the cache memory 116 can be incorporated into the processor core 112 respectively. The system 100 may include more than one processor/processing core in another embodiment of the invention. In another embodiment of the invention, the non-volatile memory 138 may perform a similar function as the non-volatile memory 180 and has a similar LTP address mapping table. In addition, there are other functional blocks or more instances of each block that can be connected in system 100 that are not shown.

FIG. 2 illustrates the modules 200 in a system 100 to implement the methods disclosed herein in accordance with one embodiment of the invention. The modules 200 include, but are not limited to, the logic block 205, the memory 130, and the non-volatile memory 180. The logic block 205 has three modules that include the power-fail recovery manager 210, the memory manager 220 and the non-volatile memory manager 230. The memory manager couples with the memory 130 and it manages the amount of memory in the volatile memory 132 that can be allocated for the cached LTP address mapping table 134.

In one embodiment of the invention, when the system 100 is initialized, the memory manager 220 divides a portion of the available memory space in the volatile memory 132 into a number of buffers. In one embodiment of the invention, the allocation of the available memory space is fixed. In another embodiment of the invention, the memory manager 220 has the ability to add or delete buffers dynamically during the operation of the system 100. In one embodiment of the invention, if the system 100 supports paging of the non-volatile memory 180, the size of each buffer is set as the page size of the non-volatile memory 180. Each buffer or frame in the volatile memory 132 can hold or store a segment of the LTP address mapping table 182 in the non-volatile memory 180. The memory manager 220 has the ability to add and/or remove cached segments of the LTP address mapping table 182 as needed from the cached LTP address mapping table 134. The memory manager 220 also tracks dirty cached segments of the cached LTP address mapping table 134, i.e., cached segments that have been updated in the cached LTP address mapping table 134 but has not been saved to the LTP address mapping table 182, and manages the flushing of these dirty cached segments to the LTP address mapping table 182.

In one embodiment of the invention, the lookup table 136 or segment table allows the memory manager 220 to determine where each segment of the LTP address mapping table associated with the non-volatile memory 180 is located, i.e., determine if a particular segment is cached in the cached LTP address mapping table 134 in the volatile memory 132 or stored in the LTP address mapping table 182 in the non-volatile memory 180. When the memory manager 220 receives a request to access an entry or a logical address of the LTP address mapping table, it determines which particular segment of the LTP address mapping table where the logical address belongs. After the particular segment is determined, the memory manager 220 checks the location of the particular segment from the lookup table 136.

In one embodiment, if the lookup table 136 indicates that the particular segment of the LTP address mapping table is not cached in the cached LTP address mapping table 134, i.e., the particular segment is in the LTP address mapping table 182 in the non-volatile memory 180, the memory manager 220 determines if any of the buffers in the volatile memory 132 is unused or available. If there is an unused buffer, the memory manager 220 caches the particular segment from the LTP address mapping table 182 in the non-volatile memory 180 into the unused buffer in the volatile memory 132. If there is no unused buffer, memory manager 220 selects one or more cached segments in the cached LTP address mapping table 134 to be evicted to the non-volatile memory 180 based on a caching policy and evicts the selected one or more segments in the cached LTP address mapping table 134 to the non-volatile memory 180.

After evicting the selected one or more segments, the memory manager 220 caches the particular segment from the LTP address mapping table 182 into the evicted one or more segments in the cached LTP address mapping table 134. In one embodiment of the invention, the memory manager 220 has the ability to pin or lock one or more cached segments in the cached LTP address mapping table 134 to prevent the pinned segment(s) from paging to the non-volatile memory 180. This allows critical Logical Block Addresses (LBAs) to be pinned in the volatile memory 130 and it eliminates the potential extra non-volatile memory 180 accesses if the segment containing the LBAs is not in the cached LTP address mapping table 134. The performance of the system 100 and the lifespan of the non-volatile memory 180 can be enhanced when the memory manager 220 supports the pinning of one or more cached segments in the cached LTP address mapping table 134.

The non-volatile memory manager 230 is coupled to the non-volatile memory 180 and is responsible for reading from and writing to a segment(s) of the LTP address mapping table 182. In one embodiment of the invention, the non-volatile memory manager 230 accesses the non-volatile memory 180 via paging. In another embodiment of the invention, the non-volatile memory manager 230 accesses the non-volatile memory 180 via individual memory line access. One of ordinary skill in the relevant art will readily appreciate that other methods of accessing the non-volatile memory 180 can also be used without affecting the workings of the invention.

In one embodiment of the invention, when the non-volatile memory manager 230 receives a read request of a particular segment in the LTP address mapping table 182, it checks the page address of the particular segment specified in the read request and retrieves the particular segment accordingly. In one embodiment of the invention, the page address of the particular segment is obtained from the lookup table 136 by the memory manager 220 and the memory manager 220 sends the read request with the page address of the particular segment to the non-volatile memory manager 230.

The management of a write request of a particular segment in the non-volatile memory 180 is dependent on the type of memory of the non-volatile memory 180. For example, in one embodiment of the invention, the non-volatile memory 180 is a NAND flash memory. Although a NAND flash memory can be read or programmed one byte or one at a time, erasing the contents of the NAND flash memory is performed by erasing an erase block at a time. When the non-volatile memory manager 230 receives a write request of a particular segment in the LTP address mapping table 182, it checks for an erase block in the non-volatile memory 180 that does not have any user data and writes the particular segment to the erase block.

By writing segment(s) of the LTP address mapping table 182 to an erase block with no user data, it avoids a potential deadlock condition in one embodiment of the invention. For example, a deadlock condition can arise when a relocation, i.e., moving all valid data out of an erase block and erasing the erase block, is needed before a particular segment can be paged out of the cached LTP address mapping table 134 to the non-volatile memory 180. The relocation may require a segment of the cached LTP address mapping table 134 to be paged in but all the segments of the cached LTP address mapping table 134 are currently dirty.

In the event of insufficient erased capacity in the non-volatile memory 180, the non-volatile memory manager 230 enables the relocation process to select an erase block that only contains segments of the LTP address mapping table 182 and not user data. This is because erase blocks that contains user data may potentially require additional paging in of cached segments of the LTP address mapping table 134. This policy allows the non-volatile memory manager 230 to make forward progress until sufficient erased space exists to resume normal relocation policies. One of ordinary skill in the relevant art will readily appreciate that other types of write management techniques can applied for other types of non-volatile memory and these write management techniques can be applied without affecting the workings of the invention.

The power-fail recovery manager 210 is coupled with the memory manager 220 and the non-volatile memory manager 230. In the event of a power failure to the system 100, the power-fail recovery manager 210 ensures the data integrity of the LTP address mapping table associated with the non-volatile memory 180 is maintained. In one embodiment of the invention, the power-fail recovery manager 210 recovers the LTP address mapping table associated with the non-volatile memory 180 after an power fail or crash event to the system 100.

In one embodiment of the invention, when the volatile memory 132 has sufficient capacity to store the entire LTP address mapping table, the power-fail recovery manager 210 temporarily allocates buffers in the volatile memory 132 to rebuild the LTP address mapping table. After the LTP address mapping table is rebuilt, the entire LTP address mapping table is paged to the non-volatile memory 180 and the allocated buffers are freed. In another embodiment of the invention, when the volatile memory 132 has insufficient capacity to store the entire LTP address mapping table, the process described in the flowchart 900 of FIG. 9 is used.

Although the memory manger 220, non-volatile memory manager 230 and the power-fail recovery manager 210 are illustrated and described as separate logic blocks, it is not meant to be limiting. In another embodiment of the invention, the memory manger 220, non-volatile memory manager 230 and the power-fail recovery manager 210 are integrated into one logic block. In yet another embodiment, the memory manger 220 is integrated with the memory 130. Similarly, the non-volatile memory manager 230 can be integrated with the non-volatile memory 180 in another embodiment of the invention. The memory manger 220, non-volatile memory manager 230 and the power-fail recovery manager 210 can be implemented as hardware, firmware, software, or any combination thereof. In one embodiment of the invention, the memory manger 220, non-volatile memory manager 230 and the power-fail recovery manager 210 are implemented as a block storage driver in an operating system executing on the system 100. One of ordinary skill in the relevant will readily appreciate that other variations in the placement or location of the memory manger 220, non-volatile memory manager 230 and the power-fail recovery manager 210 can be used without affecting the workings of the invention.

FIG. 3 illustrates an arrangement 300 of a LTP address mapping table 305 in accordance with one embodiment of the invention. The LTP address mapping table 305 allows the system 100 to determine the physical page address of any given logical page address of the non-volatile memory 180. In one embodiment of the invention, LTP address mapping table 305 is divided into a number of segments or sections. This allows one or more parts or portions of the LTP address mapping table 305 to be cached in a different storage area. For example, in one embodiment of the invention, the LTP address mapping table 305 is divided into six segments 310, 312, 314, 316, 318, and 320. Although the segments 310, 312, 314, 316, 318, and 320 are illustrated in sequential sequence, the storage of each segment may be not be stored in contiguous parts of the non-volatile memory 180. For example, if the non-volatile memory 180 is a NAND flash memory, segment 0 310 and segment 1 312 may be stored in one erase block and segments 314, 316, 318, and 320 may be stored in another erase block.

Each segment of the LTP address mapping table 305 has one or more LTP entry and each LTP entry represents a particular mapping of a logical address to a physical address of the non-volatile memory 180. In one embodiment of the invention, the number of LTP entries per segment is set to the ratio of the page size in bytes of the non-volatile memory 180 to the size of each LTP entry in bytes. This allows each segment of the LTP address mapping table 305 to be saved or stored into a single page of the non-volatile memory 180. For example, if the size of each page of the non-volatile memory 180 is 8 kilobytes(kb) and the size of each LTP entry is 4 bytes, the number of LTP entries per segment is (8×1024 bytes)/4 bytes=2048. An LTP address mapping table of N entries and S LTP entries per segment is divided into N/S segments. Segment 2 314 is illustrated in an expanded view and LTP[x] 350 and LTP[x+1] 352 depict the first and second LTP entries of segment 2 314 respectively. Segment 2 314 has s entries and LTP[x+s−2] 354 and LTP[x+s−1] 356 depict the penultimate and ultimate entries of segment 2 314 respectively.

By setting the size of each segment of the LTP address mapping table 305 to a page size of the non-volatile memory 180, it allows simple and efficient implementation in the system 100. In another embodiment of the invention, the size of each segment of the LTP address mapping table 305 is set to a multiple of a page size of the non-volatile memory 180. For example, in one embodiment of the invention, the size of each segment can be set as the size of three pages of the non-volatile memory 180. In another embodiment of the invention, the segments of the LTP address mapping table 305 have unequal sizes. One of ordinary skill in the relevant art will readily appreciate that other variations of the size of each segment of the LTP address mapping table 305 can be utilized without affecting the workings of the invention.

FIG. 4 illustrates an arrangement 400 of a lookup table 136 in accordance with one embodiment of the invention. In the example of FIG. 4, the entire LTP address mapping table associated with the non-volatile memory 180 is stored in LTP address mapping table 182. In another embodiment of the invention, LTP address mapping table 182 stores only the segments of the LTP address mapping table that are not cached in the cached LTP address mapping table 134.

After the LTP address mapping table 182 is divided into segments, the memory manager 220 can cache some segments of the LTP address mapping table 182 into the cached LTP address mapping table 134 in one embodiment of the invention. To monitor or keep track of each segment, a lookup table 136 or segment table allows the system 100 to determine if the LTP information that it requires resides in the non-volatile memory 180 or in the memory 130 and determine the location of the LTP information on the appropriate media.

By facilitating the caching of one or more segments of the LTP address mapping table 182 in the cached LTP addressing mapping table 134, the memory manager 220 allows a volatile memory 130 of a smaller capacity than LTP address mapping table 182 to be utilized while enabling the LTP addressing scheme. For example, if the volatile memory 130 has a capacity of 1 megabytes and the LTP address mapping table 182 requires 2 megabytes of memory space, the memory manager 220 is able to cache only some portions of the LTP address mapping table 182 in the volatile memory 130 and stores the remaining portions of the LTP address mapping table 182 in the non-volatile memory 180 in one embodiment of the invention.

For the purposes of illustration, the memory 130 and the non-volatile memory 180 are assumed to be DRAM and NAND flash memory respectively. The memory manager 220 is assumed to cache segment 0 310, segment 3 316 and segment 5 320 of the LTP address mapping table 182 in the cached LTP address mapping table 134. The memory manager 220 creates and maintains a lookup table that allows it to keep track of the location of each segment of the LTP address mapping table. The i-th entry of the lookup table 136 specifies whether the i-th segment is in the memory 130 or in the non-volatile flash memory 180.

In one embodiment of the invention, the memory manager 220 stores a pointer to each segment of the LTP address mapping table 182 cached in the cached LTP address mapping table 134. Pointers 411, 414 and 416 in lookup table 136 are directed to segment 0 310, segment 3 316 and segment 5 320 respectively. For example, in one embodiment of the invention, when the memory manager 220 receives an request to access an entry in segment 0 of the LTP address mapping table 182, it checks or reads the first entry of the lookup table 136 to obtain a pointer to segment 0 in the cached LTP address mapping table 134.

In one embodiment of the invention, the memory manager 220 stores a physical page address of each segment of the LTP address mapping table 182 not cached in the cached LTP address mapping table 134. Physical page addresses 412, 413 and 415 in lookup table 136 are directed to segment 1 312, segment 2 314 and segment 4 318 respectively. For example, in one embodiment of the invention, when the memory manager 220 receives an request to access an entry in segment 4 of the LTP address mapping table 182, it checks or reads the fifth entry of the lookup table 136 to obtain a physical page address of segment 4 in the LTP address mapping table 182.

Although the lookup table 136 is depicted to use only pointers and physical page addresses to indicate or specify the location of each segment of the LTP address mapping table, it is not meant to be limiting. One of ordinary skill in the relevant art will readily appreciate that other techniques or methods of indicating the location of each segment of the LTP address mapping table can be used without affecting the workings or the scope of the invention.

FIG. 5A illustrates a flowchart 500 of the operations to look up an entry of a LTP addressing mapping table. In step 505, the memory manager 220 receives an access request of an entry or a logical address of the LTP addressing mapping table associated with non-volatile memory 180. In step 510, the memory manager 220 determines which segment of the LTP addressing mapping table where the logical address belongs. In one embodiment of the invention, the memory manager 220 uses the ratio of the logical address to be accessed to the number of entries per segment of the LTP addressing mapping table to determine which segment of the LTP addressing mapping table where the logical address belongs. For example, in one embodiment of the invention, if the number of entries per segment of the LTP addressing mapping table is 2048 and the logical address of the access request is 9044, the memory manager 220 performs an integer division of the ratio of 9044/2048 to obtain 4, i.e., the logical address of 9044 belongs to the fourth segment of the LTP addressing mapping table.

In step 515, the memory manager 220 checks the location of the segment determined in step 510 from the lookup table. In step 520, the memory manager 220 checks if the lookup table 136 indicates that the location of the segment is in the cached LTP address mapping table 134 in the volatile memory 132. If yes, the memory manager 220 determines the offset in the segment corresponding to the logical address of the access request in step 522. In step 524, the memory manager 220 returns the physical page address corresponding to the logical address of the access request and the flow 500 ends.

If in step 520, the lookup table 136 does not indicate that the location of the segment is in the cached LTP address mapping table 134 in the volatile memory 132, i.e., the segment is in the LTP address mapping table 182 in the non-volatile memory 180, the memory manager 220 identifies a buffer in the volatile memory 132 to cache the segment from the non-volatile memory 180 in step 525. In step 530, the memory manager 220 sends a read request of the segment to the non-volatile memory manager 230 and caches the segment from the LTP address mapping table 182 in the non-volatile memory 180 into the volatile memory 132. The memory manager 220 returns the physical page address corresponding to the logical address of the access request and the flow 500 ends. One of ordinary skill in the relevant art will readily appreciate that some of the steps in flow 500 may also be arranged in a different sequence or may be executed in parallel.

FIG. 5B illustrates a flowchart 550 of the operations to identify a buffer in a volatile memory to cache a segment of a LTP addressing mapping table from a non-volatile memory in accordance with one embodiment of the invention. In step 555, the memory manager 220 checks if there are any free buffers in the volatile memory 132. If yes, the memory manager 220 selects one of the free buffers as the identified buffer in step 560 and the flow goes to step 530. In one embodiment of the invention, the selection of the free buffers is based on a policy that includes but is not limited to, a least recently used policy, and the like. If no, the memory manager 220 selects one of the used buffers in the volatile memory 132 based on a caching policy in step 565. The caching policy includes, but is not limited to, a least recently used (LRU) policy, a first in first out (FIFO) policy, and the like.

In step 570, the memory manager 220 checks if the segment in the selected buffer is dirty. If no, the memory manager 220 sets the selected buffer as the identified buffer in step 585 and the flow 550 goes to step 530. If yes, the memory manager 220 evicts the segment in the selected buffer to the LTP addressing mapping table 182 in the non-volatile memory 180. In step 580, the memory manager 220 sets the evicted buffer as the identified buffer and the flow 550 goes to step 530.

FIG. 6 illustrates a pseudo code 600 of the operations to look up an entry of a LTP addressing mapping table in accordance with one embodiment of the invention. One of ordinary skill in the relevant art will appreciate the workings of the pseudo code 600 and therefore the pseudo code 600 shall not be described in detail herein.

FIG. 7 illustrates an optimized lookup table 700 in accordance with one embodiment of the invention. In one embodiment of the invention, an optimization to the LTP address mapping table associated with a non-volatile memory 180 can be made when the L2P entries in a particular segment are pointing to sequential physical addresses. In such a scenario, the entry for the particular segment in the lookup table 700 can store or specify the physical address corresponding to the first logical page in that particular segment and marks the particular segment as optimized. For example, in a segment having S logical pages, if the logical pages 0 to S−1 in the segment are mapped to physical address pages X to X+S−1, the memory manager 220 marks the entry in the lookup table as optimized and stores the physical page address X in the entry. This is illustrated as element 710 of the lookup table 700. This optimization effectively compresses the LTP address mapping table in the non-volatile memory 180, and eliminates the need to access the non-volatile memory 180 to retrieve the entries of the segment. For example, when the memory manger 220 receives an access request of a logical address in segment 2 of the LTP address mapping table, it checks the lookup table 700 and obtains a physical page address. As the entry 710 is optimized, the memory manager 220 can easily determine the physical page address corresponding to the logical address by adding the offset of the logical address in segment 2 with obtained physical page address.

In one embodiment of the invention, the system 100 performs defragmentation to allow the optimization to occur more frequently. Files such as video files, audio files, and the like, typically has relatively large sizes and are written sequentially and physically contiguous on the non-volatile memory 180. These large files can benefit from the optimization of the LTP address mapping table.

FIG. 8 illustrates a pseudo code 800 of the operations to look up an entry of a LTP addressing mapping table in accordance with one embodiment of the invention. The pseudo code 800 includes additional code that is highlighted in bold font to lookup an optimized lookup table 700. One of ordinary skill in the relevant art will readily appreciate the workings of the pseudo code 800 and therefore the pseudo code 800 shall not be described in detail herein.

FIG. 9 illustrates a flowchart 900 of the operations to recover a LTP address mapping system in accordance with one embodiment of the invention. Flowchart 900 illustrates a scenario when there is insufficient volatile memory 132 to rebuild the LTP address mapping table associated with a NAND flash memory. In step 905, the power-fail recovery manager 210 scans all erase blocks (EBs) of the NAND flash memory to identify the EB(s) containing segments of the LTP address mapping table and any pre-erased EB(s). In step 910, the power-fail recovery manager 210 rebuilds the lookup table using the identified EBs containing segments of the LTP address mapping table.

In step 915, the power-fail recovery manager 210 rebuilds the LTP address mapping table by paging segments of the LTP address mapping table to unused buffers in the volatile memory. In step 920, the power-fail recovery manager 210 checks if all the buffers in the volatile memory are used. If no, the flow 900 goes back to step 915. If yes, the flow goes to step 925 and the power-fail recovery manager 210 checks if there are any pre-erased EBs in the NAND flash memory. If no, the power-fail recovery manager 210 identifies and erases EBs in the NAND flash memory in step 930 and the flow goes to step 935. If yes, the power-fail recovery manager 210 writes one or more dirty segments of the LTP address mapping table to an erased EB in step 935 and the flow ends.

Although the methods and techniques disclosed herein are with reference to a LTP address mapping structure, it is not meant to be limiting. In another embodiment of the invention, the methods and techniques disclosed herein may be also be applied to other data structures such as an EB state array and the like, without affecting the workings of the inventions. One of ordinary skill in the relevant art will readily appreciate how to adapt the methods and techniques disclosed herein to other data structures and these data structures are within the scope of this invention.

Although examples of the embodiments of the disclosed subject matter are described, one of ordinary skill in the relevant art will readily appreciate that many other methods of implementing the disclosed subject matter may alternatively be used. In the preceding description, various aspects of the disclosed subject matter have been described. For purposes of explanation, specific numbers, systems and configurations were set forth in order to provide a thorough understanding of the subject matter. However, it is apparent to one skilled in the relevant art having the benefit of this disclosure that the subject matter may be practiced without the specific details. In other instances, well-known features, components, or modules were omitted, simplified, combined, or split in order not to obscure the disclosed subject matter.

The term “is operable” used herein means that the device, system, protocol etc, is able to operate or is adapted to operate for its desired functionality when the device or system is in off-powered state. Various embodiments of the disclosed subject matter may be implemented in hardware, firmware, software, or combination thereof, and may be described by reference to or in conjunction with program code, such as instructions, functions, procedures, data structures, logic, application programs, design representations or formats for simulation, emulation, and fabrication of a design, which when accessed by a machine results in the machine performing tasks, defining abstract data types or low-level hardware contexts, or producing a result.

The techniques shown in the figures can be implemented using code and data stored and executed on one or more computing devices such as general purpose computers or computing devices. Such computing devices store and communicate (internally and with other computing devices over a network) code and data using machine-readable media, such as machine readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and machine readable communication media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals, etc.).

While the disclosed subject matter has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications of the illustrative embodiments, as well as other embodiments of the subject matter, which are apparent to persons skilled in the art to which the disclosed subject matter pertains are deemed to lie within the scope of the disclosed subject matter. 

1. An apparatus comprising: a NAND flash memory; a logical-to-physical (LTP) address mapping structure associated with the NAND flash memory, the structure including one or more segments; and a controller coupled with the NAND flash memory to facilitate paging of the one or more segments of the structure to the NAND flash memory.
 2. The apparatus of claim 1, wherein a size of each segment of the LTP address mapping structure is the same as or a multiple of a page size of the NAND flash memory.
 3. The apparatus of claim 1, wherein the controller to facilitate paging of the one or more segments of the structure is to: receive a request to write the one or more segments to the NAND flash memory; determine that an erase block of the NAND flash memory is available responsive to receiving the request; and write at least one of the one or more segments to the determined erase block.
 4. The apparatus of claim 1, wherein the controller is a block storage driver.
 5. A system comprising: a NAND flash memory to store a plurality of sections of an indirection system map of the NAND flash memory; and logic to cache one or more of the plurality of sections of the indirection system map in a memory in the system.
 6. The system of claim 5, wherein the logic is further to store a lookup table in the memory, the lookup table associated with the indirection system map to indicate a location of each section of the indirection system.
 7. The system of claim 5, wherein the indirection system map comprises a logical-to-physical address mapping structure of the NAND flash memory.
 8. The system of claim 6, wherein a size of each section of the indirection system map is equal to or a multiple of a page size of the NAND flash memory.
 9. The system of claim 8, wherein the logic to store the lookup table is to: store a pointer to each section of the indirection system map cached in the memory; and store a physical page address of each section of the indirection system map not cached in the memory.
 10. The system of claim 8, wherein the logic is further to determine that one section of the indirection system not cached in the memory comprises contiguous physical addresses for all entries in the one section, and wherein the logic to store the lookup table is to: store a physical address corresponding to a first entry of a logical address of the determined section; and indicate the determined one section as optimized.
 11. The system of claim 8, wherein the logic is further to divide an unused portion of the memory into a plurality of buffers, and wherein the logic to cache the one or more sections of the indirection system map in the memory is to cache the one or more sections of the indirection system map into the plurality of buffers.
 12. The system of claim 11, wherein the logic is further to: determine that the lookup table is to indicate that a section of the indirection system to be accessed is not cached in the memory; and determine if any of the plurality of buffers in the memory is unused, if so, cache the section of the indirection system to be accessed from the NAND flash memory into the determined unused buffer in the memory; and if not so, select one or more sections of the indirection system cached in one or more respective buffers to be evicted to the NAND flash memory based on a caching policy; evict the selected one or more sections of the indirection system to the NAND flash memory; and cache the section of the indirection system to be accessed from the NAND flash memory into the one or more respective buffers of the memory.
 13. The system of claim 5, wherein the logic is further to pin at least one of the cached one or more sections of the indirection system map in the memory, wherein the pinned segment is prevented from paging to the NAND flash memory.
 14. The system of claim 5, wherein the memory is one of Synchronous Dynamic Random Access Memory, Dynamic Random Access Memory, RAMBUS DRAM and Double Data Rate three SDRAM.
 15. A method comprising: partitioning a logical-to-physical (LTP) indirection map of a non-volatile memory into a plurality of segments; and paging at least one segment of the LTP indirection map to the non-volatile memory responsive to the partitioning.
 16. The method of claim 15, wherein partitioning the LTP indirection map of the non-volatile memory into the plurality of segments comprises partitioning the LTP indirection map of the non-volatile memory into a plurality of page-sized segments.
 17. The method of claim 15, further comprising maintaining a segment table associated with the LTP indirection map, wherein the segment table is to specify where each segment of the LTP indirection map is located.
 18. The method of claim 15, wherein the non-volatile memory is a NAND flash memory, and wherein paging the at least one segment of the LTP indirection map to the NAND flash memory comprises: determine that an erase block of the NAND flash memory does not contain any user data; and write the at least one segment of the LTP indirection map to the determined erase block.
 19. The method of claim 15 further comprising: receiving a notification of power failure of the non-volatile memory; determining that a size of the LTP indirection map is less than an unutilized memory space in a memory in response to receiving the notification; building another LTP indirection map in the unutilized memory space in the memory; and paging the other built LTP indirection map to the non-volatile memory.
 20. The method of claim 17, wherein the non-volatile memory is a NAND flash memory, further comprising: receiving a notification of power failure of the non-volatile memory; determining that a size of the LTP indirection map is more than an unutilized memory space in a memory in response to receiving the notification; identifying one or more erase blocks of the NAND flash memory storing the one or more segments of the LTP indirection map; and building the segment table using the one or more stored segments of the LTP indirection map in the identified one or more erase blocks. 